fix: make client-owned web fetch discoverable (#252) - #263

Fixes #252.

The problem

webcmd web fetch always works, but the CLI never tells you it exists.

The command is intercepted on the client-owned fast path in src/main.ts:79, before adapter discovery — so it runs on a fresh install with zero plugins. It just isn't listed anywhere, and asking for help throws:

$ webcmd --help                       # no `web` under Commands or Site adapters
$ webcmd list                         # no web fetch
$ webcmd list -f json                 # 0 entries with "site": "web"
$ webcmd --get-completions webcmd web # (empty)
$ webcmd web fetch --help
ArgumentError: --url must be an http or https URL

So the only way to discover a built-in command is to already know it.

What I changed

1. clis/web/fetch.js — registers the command through a new makeWebFetchCommand() factory, so both build-manifest and the runtime filesystem scan pick it up.
2. src/discovery.ts — the module pattern now matches make<Pascal>Command(, the same convention src/build-manifest.ts:48 already used.
3. cli-manifest.json — gains the generated web/fetch entry. It regenerates byte-identical, check:hosted-contract passes, and hosted-contract.json is unchanged because this command is not browser-based.
4. src/fetch/command.ts — now that help is real, the fast path honours what it advertises: -f/--format for output (markdown still the default), structured --help -f yaml|json, an error on an unsupported format instead of silently falling back to a table, and an error when --timeout/--max-chars is given a flag-shaped value instead of quietly coercing it to 1.

The fast path itself stays exactly where it was — execution never touches the registry, so hosted mode still never cloud-routes this command.

Proof

Verified against a rebuilt dist. Four new tests in src/fetch/command.test.ts cover the -f output path, structured help, the format rejection and the --timeout -5 rejection. Full suite passes except tests/e2e/plugin-management.test.ts, which clones plugins over the network and fails identically on main (fixed separately in #267).

Not in this PR

• [Bug]: webcmd web fetch prints a raw Node stack trace instead of a formatted CLI error #246 — ArgumentError still prints a raw stack trace on the fast path.
• [Bug]: web fetch-browser is not installed by default, so the FETCH_BLOCKED escalation path is a dead end #247 — clis/ missing from package.json files. Unreachable here while the argv[0] === 'web' && argv[1] === 'fetch' prefix holds, and pre-existing for fetch-browser. Fixed in fix: ship web fetch-browser so the blocked-fetch escalation works (#247) #271.

🤖 Generated with Claude Code